EnhancedLocaleSupport

Boolean

false

Purpose

The EnhancedLocaleSupport parameter enables handling of standard client and presentation client locale-sensitive formatting of date, time, and numeric values (that is, numbers and currency) to be standardized and the regional overrides set on the presentation client to be forwarded to the application server so that both nodes use a consistent set of locale settings for the application when running in JADE thin client mode.

Enhanced locale support is enabled (or disabled) throughout a complete JADE environment, with the single setting in the JADE initialization file on the database node.

All client nodes and presentation clients share the same single setting.

The required languages must be installed on both the application server and the presentation client to ensure consistent behavior (for example, sorting and comparison) between the presentation client and the application server.

When this parameter is not defined or it is set to the default value of false:

Calling some methods can cause inconsistent results to be returned to the application server when running in JADE thin client mode and there are regional overrides, as all overrides on the application server are suppressed.
The Application class setJadeLocale method does not change the current locale used for date, time, numeric, and currency parsing and formatting.
The two-digit edit mask year of 'yy' is calculated using the current century.

When the EnhancedLocaleSupport parameter is set to true:

The required language or languages must be installed on both the application server and the presentation client, to ensure consistent behavior (for example, sorting and comparison) between the presentation client and the application server.
Presentation client regional overrides are applied.
Locale-sensitive values (for example, the Date primitive type monthName method) return the values for the current thread locale, which is changed when the Application class setJadeLocale method is called.
The Windows Control Panel setting is used to convert a two-digit year into a four-digit year for a two-digit edit mask year of 'yy'. By default, years:
- 00 through 29 become 2000 through 2029
- 30 through 99 become 1930 through 1999
The values returned from the Application class currentLocaleInfo property reflect the regional overrides that have been applied to the session locale, if currently in use.
The Schema class getLocaleFullInfo method and its associated methods recognize the LCID_SessionWithOverrides global constant value, which enables you to retrieve information from the session locale without having to save the initial locale for the call.
Additional conversion routines have been added to fully support (binary‑to‑string‑to‑binary) value round trips; for example, the Decimal primitive type parseCurrencyWithFmtAndLcid and userCurrencyFormatAndLcid methods, and the Time primitive type parseWithFmtAndLcid and userFormatAndLcid methods.
TextBox class dataType property values for currency, short date, long date, and time ensure that entered values are limited to match the current locale formatting for each type.

Parameter is read when …

The database node initializes.